Computing nodes

ABSTRACT

In examples provided herein, upon receiving notification of a computational task requested by a package to provide an experience to a user, a remote node management engine identifies computing nodes for performing the computational task and determining available processing resources for each computing node, where a computing node resides at networked wearable devices associated with the user. The remote node management engine further selects one of the computing nodes as a primary controller to distribute portions of the computational task to one or more of the other computing nodes and receive results from performance of the portions of the computational task by the other computing nodes, and provides to the selected computing node information about available processing resources at each computing node.

BACKGROUND

In many arenas, disparate tools can be used to achieve desired goals.The desired goals may be achieved under changing conditions by thedisparate tools.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various examples of the principlesdescribed below. The examples and drawings are illustrative rather thanlimiting.

FIG. 1 depicts an example environment in which a context-aware platformthat performs computing node functions may be implemented.

FIG. 2A depicts a block diagram of example components of a remote nodemanagement engine.

FIG. 2B depicts a block diagram depicting an example memory resource andan example processing resource for a remote node management engine.

FIG. 3A depicts a block diagram of example components of a computingnode, such as a networked wearable device or access point.

FIG. 3B depicts a block diagram depicting an example memory resource andan example processing resource for a computing node.

FIG. 4 depicts a block diagram of an example context-aware platform.

FIG. 5 depicts a flow diagram illustrating an example process ofidentifying and selecting a networked wearable device associated with auser to act as a primary controller to coordinate performance of acomputational task for a package for a user experience.

FIG. 6 depicts a flow diagram illustrating an example process ofdetermining a backup controller for a malfunctioning primary controller.

FIG. 7 depicts a flow diagram illustrating an example process ofdetermining suitable access points for performing a computational taskfor a package.

FIGS. 8A and 8B depict a flow diagram illustrating an example process ofa primary controller distributing portions of a computational task tocomputing nodes.

FIG. 9 depicts an example system including a processor andnon-transitory computer readable medium of a remote node managementengine.

FIG. 10 depicts an example system including a processor andnon-transitory computer readable medium of a computing node.

DETAILED DESCRIPTION

As technology becomes increasingly prevalent, it can be helpful toleverage technology to integrate multiple devices, in real-time, in aseamless environment that brings context to information from variedsources without requiring explicit input. Various examples describedbelow provide for a context-aware platform (CAP) that supports remotemanagement of one or more computing nodes, hosted at a networkedwearable device (NWD) associated with a user or other device in closeproximity to a user's networked devices. The user can be a person, anorganization, or a machine, such as a robot. The computing nodes providecomputational resources that can allow for faster responses tocomputationally intense tasks performed in support of providing aseamless experience to the user, as compared to processing performed ina centralized computation model, such as cloud computation, which canintroduce latency into the computation process. As used herein, “CAPexperience” and “experience” are used interchangeably and intended tomean the interpretation of multiple elements of context in the rightorder and in real-time to provide information to a user in a seamless,integrated, and holistic fashion. In some examples, an experience or CAPexperience can be provided by executing instructions on a processingresource at a computing node. Further, an “object” can include anythingthat is visible or tangible, for example, a machine, a device, and/or asubstance.

The CAP experience is created through the interpretation of one or morepackages. Packages can be atomic components that execute functionsrelated to devices or integrations to other systems. As used herein,“package” is intended to mean components that capture individualelements of context in a given situation. In some examples, theexecution of packages provides an experience. For example, a packagecould provide a schedule or a navigation component, and an experiencecould be provided by executing a schedule package to determine a user'sschedule, and subsequently executing a navigation package to guide auser to the location of an event or task on the user's schedule. Asanother example, another experience could be provided by executing afacial recognition package to identify a face in an image by comparingselected facial features from the image with data in a facial database.

In some examples, the platform includes one or more experiences, each ofwhich correspond to a particular application, such as a user'soccupation or a robot's purpose. In addition, the example platform mayinclude a plurality of packages which are accessed by the variousexperiences. The packages may, in turn, access various information froma user or other resources and may call various services, as described ingreater detail below. As a result, the user can be provided withcontextual information seamlessly with little or no input from the user.The CAP is an integrated ecosystem that can bring context to informationautomatically and “in the moment.” For example, CAP can sense, retrieve,and provide information from a plurality of disparate sensors, devices,and/or technologies, in context, and without input from a user.

Elements shown in the various figures herein can be added, exchanged,and/or eliminated so as to provide a number of additional examples ofthe present disclosure. In addition, the proportion and the relativescale of the elements provided in the figures are intended to illustratethe examples of the present disclosure, and should not be taken in alimiting sense.

FIG. 1 depicts an example environment in which a context-aware platform(CAP) 130 that includes a remote node management engine 135 for managingcomputational tasks performed at remote computing nodes may beimplemented.

Wearable devices can include any number of portable devices associatedwith a user of the devices that have a processor and memory and arecapable of communicating wirelessly by using a wireless protocol, suchas WiFi or Bluetooth. Examples of wearable devices include a smartphone,tablet, laptop, smart watch, electronic key fob, smart glass, and anyother device or sensor that can be attached to or worn by a user. When auser's wearable devices are configured to communicate with each other,for example, as indicated by wearable device communication network 111in FIG. 1, the devices are referred to herein as networked wearabledevices (NWDs) 110.

Access point 120 can be a standalone access point device; however,examples are not so limited, and access point 120 can be embedded in astationary device, for example, a printer, a point of sale device, etc.The access point 120 can include a processor and memory configured tocommunicate with the device in which it is embedded and to communicatewith the CAP 130 and/or networked wearable devices 110 within wirelesscommunication range. While only one access point 120 is shown in theexample of FIG. 1 for clarity, multiple access points can be locatedwithin wireless communication range of the one or more NWDs associatedwith a user.

A computing node used for performing a portion of a computational taskrequested by a package to provide an experience to a user can reside ata NWD 110 associated with that user or at an access point 120 withinwireless communication range of the user's NWDs 110. Each computing nodeincludes components, to be described below, that support performingcomputational tasks for the experience by using the available processingresources of the NWD 110 or access point 120.

In the example of FIG. 1, the CAP 130 can communicate through a network105 with one or more of the computing nodes at the NWDs 110 and/or acomputing node at the access point 120. The network 105 can be any typeof network, such as the Internet, or an intranet. The CAP 130 includes aremote node management engine 135, among other components to bedescribed below with reference to FIG. 4. The remote mode managementengine 135 supports the selection and remote management of computingnodes in close proximity to the user to provide faster responses tocomputational activities intended to support providing an experience tothe user. The experience can be user-initiated or automaticallyperformed

FIG. 2A depicts a block diagram 200 including example components of aremote node management engine 135. The remote node management engine 135can include a communication engine 212, a device status engine 214, acomputation assignment engine 216, an access point engine 218, and alearning engine 219. Each of the engines 212, 214, 216, 218, 219 canaccess and be in communication with a database 220.

Communication engine 212 may be configured to receive notification of acomputational task requested by a package to be performed in conjunctionwith providing an experience to a user. Further, the communicationengine 212 can transmit a request to a computing node at one of the NWDs110 or access points 120 associated with the user to function as aprimary controller to distribute portions of the computational task toone or more other computing nodes. The other computing nodes can resideat one of the other NWDs and/or one or more access points 120 in closeproximity to the user. For example, the computing nodes at the NWDs 110can be used if the user is not near any access points, such as when theuser is outside.

Alternatively, if the user is near one or more access points 120, forexample, inside an office building or shopping complex, thecommunication engine 212 can transmit requests directly to the one ormore access points to perform respective portions of the computationaltask. The communication engine 212 can receive results from performanceof the portions of the computational task by the computing nodes fromthe primary controller or, in some implementations, directly from thecomputing nodes and transmit the results of the computational task tothe requesting package.

In some implementations, the communication engine 212 may also beconfigured to retrieve information and/or metadata used to perform thecomputational task and to transmit the information and/or metadata tothe primary controller and/or one or more of the computing nodes. Forexample, for a facial recognition computational task, the retrievedinformation can be a facial database with corresponding identityinformation for each of the faces in the database.

The device status engine 214 may be configured to register and identifycomputing nodes at NWDs associated with a user. When a computationaltask is to be performed to support an experience to be provided to aparticular user, the device status engine 214 can determine availableprocessing resources at each NWD 110 associated with the user, andprovide to the selected NWD (primary controller) information aboutavailable processing resources at each NWD 110.

The access point engine 218 may be configured to register and identifyaccess points. Registration information can include a locationidentifier, such as global positioning (GPS) coordinates. Upon receivingnotification of a computational task requested by a package forproviding an experience to a user, the access point engine 218 mayidentify one or more suitable access points within communication rangeof the NWDs 110 associated with the user based on the location of theuser. The access point engine 218 can communicate with the appropriatelylocated access points to determine available processing resources at therespective access points. Additionally, the access point engine 218 maybe configured to provide to the selected NWD (primary controller)information about available processing resources at the access point.

Based upon the determined available processing resources at each NWD 110and access point 120, the computation assignment engine 216 may beconfigured to select one of the computing nodes at a selected NWD 110 oraccess point 120 as a primary controller or backup controller todistribute portions of the computational task to one or more of theother NWDs 110 and/or access points 120 within wireless communicationrange of the user and receive results from performance of the portionsof the computational task. In deciding which computing node todistribute portions of the computational task, the computationassignment engine 216 can take into account availability of processingresources at the computing nodes, as well as availability of storage forperforming the computational task in a timely manner. Further, thecomputation assignment engine 216 receives checkpoint information andheartbeats from the primary controller and/or the backup controller toensure that the computational task is being performed. In someinstances, the computation assignment engine 216 may cancel thecomputational task or restart the computational task.

The learning engine 219 may be configured to track capabilities of eachof the NWDs 110 and access points 120 as a computing node, such as speedwith which assigned computational tasks are performed and availablememory for use in conjunction with performing the computational tasks.Additionally, the learning engine 219 may be configured to determinefrom the tracked capabilities of specific NWDs 110 and access points 120which of the specific NWDs and access points can function as a backupcontroller for the primary controller, for example, based on trainingdata. Moreover, should the primary controller be unresponsive, forexample, because of loss of battery power or a software problem, thelearning engine 219 can select a particular one of the specific NWDs oraccess points as the backup controller to substitute for the primarycontroller.

Database 220 can store data, such as retrieved information or metadataused to perform a computational task.

FIG. 3A depicts a block diagram of example components of an examplecomputing node residing at a networked wearable device 110 or accesspoint 120. The computing node can include a node communication engine302, a controller engine 304, and a computation engine 306. Each ofengines 302, 304, 306 can interact with a database 310.

Node communication engine 302 may be configured to receive the portionof the computational task to be performed at the computing node. In someinstances, the node communication engine 302 may also receiveinformation and/or metadata to be used to perform the computationaltask.

If a computing node is selected as the primary controller, or the backupcontroller, the node communication engine 302 may also be configured toperiodically send checkpoint information and a heartbeat, to the remotenode management engine 135 of the CAP 130. Receipt of the periodicheartbeat informs the remote node management engine 135 that the primarycontroller is still functioning and able to perform the duties of theprimary controller, namely, selecting one or more computing nodes at theother NWDs and/or access points for performing portions of thecomputational task, receiving results from the performance of theportions of the computational task, and transmitting the results of thecomputational task to the requesting package.

Additionally, the node communication engine 302 can be configured toreceive the last checkpoint information sent by the primary controllerwhen performing the functions of the backup controller. In case theprimary controller fails to function properly, periodic checkpointinformation sent by the node communication engine 302 regarding thestate or progress of the computational task allows a backup controllerto resume coordinating the results of the computational task from thelast sent checkpoint.

Further, if the computing node is the primary controller or the backupcontroller, the node communication engine 302 can receive informationabout processing resources available at computing nodes at NWDs 110and/or access points 120 within communication range of the NWDs. Thisallows the controller engine 304 to determine to which computing nodesportions of the computational task should be assigned.

If the computing node is the primary or backup controller, thecontroller engine 304 may be configured to assign portions of thecomputational task to one or more computing nodes at other NWDs 110and/or access points 120 based on the availability of processingresources at those computing nodes. Otherwise, if the computing node isnot acting as the primary or backup controller, the controller engine304 does not perform any functions.

The computation engine 306 may be configured to use the availableprocessing resources at the local computing node to perform one or moreportions of the computational task, or even the entire computationaltask if processing resources at other NWDs 110 or access points 120 arenot readily available at the requested time.

Database 310 can store data, such as retrieved information or metadataused to perform a computational task, or intermediate results obtainedwhile performing the computational task.

The examples of engines shown in FIGS. 2A and 3A are not limiting, asone or more engines described can be combined or be a sub-engine ofanother engine. Further, the engines shown can be remote from oneanother in a distributed computing environment, cloud computingenvironment, etc.

In the above description, various components were described ascombinations of hardware and programming. Such components may beimplemented in different ways. Referring to FIG. 2B, the programming maybe processor executable instructions stored on tangible memory resource260 and the hardware may include processing resource 250 for executingthose instructions. Thus, memory resource 260 can store programinstructions that when executed by processing resource 250, implementsremote node management engine 135 of FIG. 2A. Similarly, referring toFIG. 3B, the programming may be processor executable instructions storedon tangible memory resource 360 and the hardware may include processingresource 350 for executing those instructions. So memory resource 360can store program instructions that when executed by processing resource350, implements the computing node portion of NWD 110 or access point120 of FIG. 3A.

Memory resource 260 generally represents any number of memory componentscapable of storing instructions that can be executed by processingresource 250. Similarly, memory resource 360 generally represents anynumber of memory components capable of storing instructions that can beexecuted by processing resource 350. Memory resource 260, 360 isnon-transitory in the sense that it does not encompass a transitorysignal but instead is made up of one or more memory componentsconfigured to store the relevant instructions. Memory resource 260, 360may be implemented in a single device or distributed across devices.Likewise, processing resource 250 represents any number of processorscapable of executing instructions stored by memory resource 260, andsimilarly for processing resource 350 and memory resource 360.Processing resource 250, 350 may be integrated in a single device ordistributed across devices. Further, memory resource 260 may be fully orpartially integrated in the same device as processing resource 250, orit may be separate but accessible to that device and processing resource250, and similarly for memory resource 360 and processing resource 350.

In one example, the program instructions can be part of an installationpackage that when installed can be executed by processing resource 250to implement remote node management engine 135 or by processing resource350 to implement the computing node portion of NWD 110 or access point120. In this case, memory resource 260, 360 may be a portable mediumsuch as a compact disc (CD), digital video disc (DVD), or flash drive ora memory maintained by a server from which the installation package canbe downloaded and installed. In another example, the programinstructions may be part of an application or applications alreadyinstalled. Memory resource 260, 360 can include integrated memory, suchas a hard drive, solid state drive, or the like.

In the example of FIG. 2B, the executable program instructions stored inmemory resource 260 are depicted as communication module 262, devicestatus module 264, computation assignment module 266, access pointmodule 268, and learning module 269. Communication module 262 representsprogram instructions that when executed cause processing resource 250 toimplement communication engine 212. Device status module 264 representsprogram instructions that when executed cause processing resource 250 toimplement device status engine 214. Computation assignment module 266represents program instructions that when executed cause processingresource 250 to implement computation assignment engine 216. Accesspoint module 268 represents program instructions that when executedcause processing resource 250 to implement access point engine 218.Learning module 269 represents program instructions that when executedcause processing resource 250 to implement learning engine 219.

In the example of FIG. 3B, the executable program instructions stored inmemory resource 360 are depicted as node communication module 362,controller module 364, and computation module 366. Communication module362 represents program instructions that when executed cause processingresource 350 to implement node communication engine 302. Controllermodule 364 represents program instructions that when executed causeprocessing resource 350 to implement controller engine 304. Computationmodule 366 represents program instructions that when executed causeprocessing resource 350 to implement computation engine 306.

FIG. 4 depicts a block diagram of an example context-aware platform(CAP) 130. The CAP 130 may determine what package among multipleavailable packages 420 to execute based on information provided by thecontext engine 456 and the sequence engine 458. In some examples, thecontext engine 456 can be provided with information from adevice/service rating engine 450, a policy/regulatory engine 452, and/orpreferences 454. For example, the context engine 456 can determine whatpackage to execute based on a device/service rating engine 450 (e.g.,hardware and/or program instructions that can provide a rating fordevices and/or services based on whether or not a device can adequatelyperform the requested function), a policy/regulatory engine 452 (e.g.,hardware and/or program instructions that can provide a rating based onpolicies and/or regulations), preferences 454 (e.g., preferences createdby a user), or any combination thereof. In addition, the sequence engine458 can communicate with the context engine 456 to identify packages 420to execute, and to determine an order of execution for the packages 420.In some examples, the context engine 456 can obtain information from thedevice/service rating engine 450, the policy/regulatory engine 452,and/or preferences 454 automatically (e.g., without any input from auser) and can determine what package 420 to execute automatically (e.g.,without any input from a user). In addition, the context engine 456 candetermine what package 420 to execute based on the sequence engine 458.

For example, based on information provided to the CAP system 130 fromthe context engine 456, the sequence engine 458, and the device/servicerating engine 450, the experience 410 may call a facial recognitionpackage 422 to perform facial recognition on a digital image of aperson's face. In some examples, the experience 410 can be initiated byvoice and/or gestures received by a NWD 110 which communicates with theCAP system 130 via network 105 (as shown in FIG. 1) to call the facialrecognition package 422, as described above. Alternatively, in someexamples, the facial recognition package 422 can be automatically calledby the experience 410 at a particular time of day, for example, 10:00pm, the time scheduled for a meeting with a person whose identity shouldbe confirmed by facial recognition. In addition, the facial recognitionpackage 422 can be called upon determination by the experience 410 thata specific action has been completed, for example, after a digital imagehas been captured by a digital camera on the NWD 110, such as can befound on a smartphone. Thus, in various examples, the facial recognitionpackage 422 can be called by the experience 410 without any input fromthe user. Similarly, other packages 420 that may need the performance ofcomputationally intensive tasks can be called by the experience 410without any input from the user.

Additionally, as facial recognition is a processing intensive task,remote node management engine 135 can select a computing node at one ofthe NWDs 110 or access points 120 as the primary controller fordistributing portions of the facial recognition task to other computingnodes, such as at one or more of the NWDs 110 and/or one or more accesspoints 120 in close proximity to the NWDs of the user.

When facial recognition package 422 is executed, it triggers the remotenode management engine 135 to call the services 470 to retrieve thefacial recognition information and/or metadata. The facial recognitioninformation and/or metadata is transmitted from the remote nodemanagement engine 135 via network 105 to the primary controller selectedby the remote node management engine 135. The primary controllersubsequently transmits the information and/or metadata to the othercomputing nodes that are assigned a portion of the facial recognitiontask. Alternatively, the primary controller can retrieve the facialrecognition information and/or metadata from the services 470. As aresult, the processing resources of multiple NWDs and access points aremade available to increase the speed at which the facial recognitiontask is performed. Moreover, by selecting computing nodes from the NWDs110 associated with the user to whom the experience 410 will be providedand access points 120 within close proximity of the NWDs 110, forexample, within wireless communication range, quicker responses to thecomputationally intense task is obtained because latency in the processis minimized. In contrast, for example, in a centralized computationmodel in the cloud, the latency in the process can significantly delaythe computations.

Performing the facial recognition task for the facial recognitionpackage 422 is one example in which one or more local computing nodescan be used to perform the processing for the task for a package. Anytype of package can request performance of a task at one or morecomputing nodes. For example, an image recognition package 424 cantrigger the remote node management engine 135 to identify computingnodes for performing an image recognition task for a digital image. Asanother example, a location package 426 can trigger the remote nodemanagement engine 135 to identify computing nodes for performing a taskfor searching a database to identify the address of a person. Theseexamples of packages are non-limiting. FIG. 5 depicts a flow diagramillustrating an example process 500 of identifying and selecting acomputing node to act as a primary controller or backup controller tocoordinate performance of a computational task for a package to providea user experience, where the computational task is performed bycomputing nodes residing at NWDs associated with the user. The primaryor backup controller can be a computing node residing at a NWDassociated with the user or at an access point embedded in a printer,point of sale device, or other computational device.

At block 505, upon receiving notification of a computational taskrequested by a package to provide an experience to a user, the remotenode management engine identifies computing nodes for performing thecomputational task and determines available processing resources foreach computing node, where the computing node resides at a NWDassociated with the user or access point within wireless communicationrange.

Then at block 510, the remote node management engine selects one of thecomputing nodes as a primary controller, where the primary controllerdistributes portions of the computational task to one or more of theother computing nodes and receives results from performance of theportions of the computational task by the other computing nodes.

At block 515, the remote node management engine provides to the selectedcomputing node information about available processing resources at eachcomputing node.

FIG. 6 depicts a flow diagram illustrating an example process 600 ofdetermining a backup controller for a malfunctioning primary controller.

At block 605, the remote node management engine tracks capabilities ofeach of the computing nodes. Then at block 610, the remote nodemanagement engine determines from the tracked capabilities specificcomputing nodes that can function as a backup controller for the primarycontroller.

At block 615, the remote node management engine, upon unresponsivenessfrom the primary controller, selects a particular one of the specificcomputing nodes as the backup controller to substitute for the primarycontroller. Unresponsiveness can be characterized as not receiving apredetermined number of consecutive heartbeat signals from the primarycontroller. The selected backup controller can continue withcoordinating the computational task from the last checkpointsuccessfully provided by the primary controller.

FIG. 7 depicts a flow diagram illustrating an example process 700 ofdetermining suitable access points for performing computational tasksfor a package. In this implementation, one or more access points can beselected to perform portions of the computational task.

At block 705, the remote node management engine identifies an accesspoint within wireless communication range of the NWDs, based on alocation of the user. Next, at block 710, the remote node managementengine communicates with the access point to determine availableprocessing resources at the access point.

At block 715, the remote node management engine provides to the selectedcomputing node acting as the primary controller information aboutavailable processing resources at the access point, where the primarycontroller further distributes a different portion of the computationaltask to the access point.

FIGS. 8A and 8B depict a flow diagram illustrating an example process800 of a primary controller distributing portions of a computationaltask to computing nodes.

At block 805, upon request for performance of a computational task by apackage to provide an experience to a user, a NWD acting as the primarycontroller or the backup controller, assigns portions of thecomputational task to one or more computing nodes, where each computingnode resides at one of the NWDs associated with the user or at an accesspoint embedded in a printer, point of sale device, or othercomputational device. An access point can also perform the functions ofthe primary controller or backup controller.

At block 810, the primary controller or the backup controller receivesresults from performance of the portions of the computational task bythe one or more computing nodes. Then at block 815, the primarycontroller or the backup controller transmits the results of thecomputational task to the requesting package.

At block 820, the primary controller or the backup controller receivesand stores information to be used for performing the computational task.

Next, at block 825, the primary controller or the backup controllerperiodically sends checkpoint information to a context-aware platform.

Then at block 830, the primary controller can perform one of theportions of the computational task.

At block 835, the primary controller receives information about theavailable processing resources at an access point within wirelesscommunication range of the NWDs, and at block 840, the primarycontroller assigns a different portion of the computational task to theaccess point.

At block 845, the primary controller receives results from performanceof the portions of the computational task by the access point, and atblock 850, the primary controller transmits the results of the portionsof the computational task performed by the access point to therequesting package.

FIG. 9 illustrates an example system 900 including a processor 903 andnon-transitory computer readable medium 981 according to the presentdisclosure. For example, the system 900 can be an implementation of anexample system such as remote node management engine 135 of FIG. 2A.

The processor 903 can be configured to execute instructions stored onthe non-transitory computer readable medium 981. For example, thenon-transitory computer readable medium 981 can be any type of volatileor non-volatile memory or storage, such as random access memory (RAM),flash memory, or a hard disk. When executed, the instructions can causethe processor 903 to perform a method of selecting a computing node as aprimary controller of other computing nodes for performing acomputational task requested by a package.

The example medium 981 can store instructions executable by theprocessor 903 to perform remote NWD management. For example, theprocessor 903 can execute instructions 982 to register and track NWDsassociated with a user and the available processing resources at theNWDs.

The example medium 981 can further store instructions 984. Theinstructions 984 can be executable to register and track access pointscapable of performing a computational task requested by a package andthe available processing resources at the access points.

The example medium 981 can further store instructions 986. Theinstructions 986 can be executable to select one of the computing nodesas a primary controller of other computing nodes that can performportions of the computational task. In addition, the processor 903 canexecute instructions 986 to perform block 510 of the method of FIG. 5.

The example medium 981 can further store instructions 988. Theinstructions 988 can be executable to communicate the computationaltask, information about available processing resources at each computingnode, and any needed information for performing the computational taskto the computing node selected as the primary controller. In addition,the processor 903 can execute instructions 988 to perform block 515 ofthe method of FIG. 5.

In some implementations, the instructions 988 can be executable tocommunicate the computational task and any needed information forperforming the computational task directly to one or more of thecomputing nodes, receive the results, and transmit the results to thepackage.

FIG. 10 illustrates an example system 1000 including a processor 1003and non-transitory computer readable medium 1081 according to thepresent disclosure. For example, the system 1000 can be animplementation of an example system such as a computing node 320 of FIG.3A residing at a NWD 110 or access point 120.

The processor 1003 can be configured to execute instructions stored onthe non-transitory computer readable medium 1081. For example, thenon-transitory computer readable medium 1081 can be any type of volatileor non-volatile memory or storage, such as random access memory (RAM),flash memory, or a hard disk. When executed, the instructions can causethe processor 1003 to perform a method of.

The example medium 1081 can store instructions executable by theprocessor 1003 to distribute portions of a computational task tocomputing nodes, such as the method described with respect to FIGS. 8Aand 8B. For example, the processor 1003 can execute instructions 1082 toassign portions of computational tasks to one or more NWDs and/or accesspoints. In addition, the processor 1003 can execute instructions 1082 toperform blocks 805 and 840 of the method of FIGS. 8A and 8B.

The example medium 1081 can further store instructions 1084. Theinstructions 1084 can be executable to communicate with the one or moreNWDs and/or access points to receive results of performing the portionsof the computational tasks and transmit the results of the computationaltask to the requesting package. Additionally, the processor 1003 canexecute instructions 1084 to perform blocks 810, 815, 845, and 850 ofthe method of FIGS. 8A and 8B.

The example medium 1081 can further store instructions 1086. Theinstructions 1086 can be executable to send checkpoint information tothe remote node management engine. The checkpoint information caninclude heartbeats and checkpoints in the performance of thecomputational task by the assigned computing nodes. In addition, theprocessor 1003 can execute instructions 1086 to perform block 825 of themethod of FIG. 8B.

The example medium 1081 can further store instructions 1088. Theinstructions 1088 can be executable to perform a portion of thecomputational task in addition to, or instead of, assigning portions ofthe computational task to other computing nodes. In addition, theprocessor 1003 can execute instructions 1088 to perform block 830 of themethod of FIG. 8B.

Not all of the steps, features, or instructions presented above are usedin each implementation of the presented techniques.

What is claimed is:
 1. A system comprising: a communication engine toreceive notification of a computational task requested by a package toprovide an experience to a user; an access point engine to identify oneor more access points within wireless communication range of networkedwearable devices (NWDs) associated with the user, and determineavailability of processing resources at the one or more access points; acomputation assignment engine to select one or more access points toperform portions of the computational task, wherein the communicationengine is further to receive results from performance of the portions ofthe computational task by the selected access points and transmit theresults to the package.
 2. The system of claim 1, further comprising: adevice status engine to identify available processing resources at theNWDs, wherein the computation assignment engine is further to select oneor more of the NWDs to perform different portions of the computationaltask.
 3. The system of claim 2, wherein the communication engine isfurther to retrieve information to be used for performing thecomputational task and transmitting the information to the selected NWDsand access points.
 4. The system of claim 1, wherein the access point isembedded in at least one of: a printer and a point of sale device.
 5. Amethod comprising: upon receiving notification of a computational taskrequested by a package to provide an experience to a user, identifyingone or more computing nodes for performing the computational task anddetermining available processing resources for each computing node,wherein a computing node resides at a networked wearable device (NWD)associated with the user; selecting one of the computing nodes as aprimary controller; and providing to the selected computing nodeinformation about available processing resources at each computing node,wherein the primary controller distributes portions of the computationaltask to one or more of the other computing nodes and receives resultsfrom performance of the portions of the computational task by the othercomputing nodes.
 6. The method of claim 5, further comprising:registering each of the NWDs, wherein registration information includesan identification of a specific associated user.
 7. The method of claim5, further comprising: based on a location of the user, identifying anaccess point within wireless communication range of the NWDs;communicating with the access point to determine available processingresources at the access point; and providing to the selected computingnode information about available processing resources at the accesspoint, wherein the primary controller further distributes a differentportion of the computational task to the access point.
 8. The method ofclaim 7, wherein the access point is embedded in at least one of: aprinter and a point of sale device.
 9. The method of claim 5, furthercomprising: tracking capabilities of each of the computing nodes; anddetermining from the tracked capabilities specific computing nodes thatcan function as a backup controller for the primary controller.
 10. Themethod of claim 9, further comprising: upon unresponsiveness from theprimary controller, selecting a particular one of the specific computingnodes as the backup controller to substitute for the primary controller.11. A non-transitory computer readable medium storing instructionsexecutable by a processing resource of a networked wearable device (NWD)of a user to: upon request for performance of a computational task by apackage to provide an experience to the user, assigning portions of thecomputational task to one or more computing nodes, wherein eachcomputing node resides at one of the NWDs associated with the user;receive results from performance of the portions of the computationaltask by the one or more computing nodes; and transmit the results of thecomputational task to the requesting package.
 12. The non-transitorycomputer readable medium of claim 11, wherein the stored instructionsfurther cause the processing resource to: receive and store informationto be used for performing the computational task.
 13. The non-transitorycomputer readable medium of claim 11, wherein the stored instructionsfurther cause the processing resource to: periodically send checkpointinformation to a context-aware platform.
 14. The non-transitory computerreadable medium of claim 11, wherein the stored instructions furthercause the processing resource to: perform one of the portions of thecomputational task.
 15. The non-transitory computer readable medium ofclaim 11, wherein the stored instructions further cause the processingresource to: receive information about available processing resources atan access point within wireless communication range of the NWDs; andassign a different portion of the computational task to the accesspoint.